Modular data processing and storage system

ABSTRACT

A system enables entities to access a single platform in order to utilize electronic data storage for storing different types of information. One or more computers may operate an electronic data storage processing network that entities can access when updating information in electronic data storage. The electronic data storage processing network may operate a plurality of electronic data storage processing modules, which can include an aggregator module, a formatter module, an operator signer module, and a validator module. Based on the specific use case for which electronic data storage is utilized, recordable data that is to be added to the electronic data storage can be processed by the appropriate aggregating, formatting, signing, and validating functions provided by the electronic data storage processing modules.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a Continuation Application of U.S. application Ser.No. 16/633,785, filed Jan. 24, 2021, which is a National Stage ofInternational Application No. PCT/US2017/044595, International FilingDate Jul. 31, 2017, of which are herein incorporated by reference.

BACKGROUND

Along with the rise of the digital world, the amount of online contentis continually increasing. To handle this increase, various mechanismsfor storing digital content have been developed. Entities can utilizeelectronic data storage to store and manage information related tovarious activities. While one benefit of the utilization of electronicdata storage is that it can be utilized by various entities for a rangeof different purposes corresponding to different types of information,this has resulted in a multitude of implementations. However, some ofthese implementations have unique characteristics that are notcompatible with certain systems. For example, if a plurality ofdifferent entities decide to implement a plurality of different types ofelectronic data storages, each of the plurality of different types ofelectronic data storages may need to be created and managed usingdifferent platforms or data. Thus, conventional systems may not be ableto easily expand usage of electronic data storage outside of specificuse cases (e.g., cryptocurrency transactions), which is limiting.

Embodiments of the invention address this and other problems,individually and collectively.

BRIEF SUMMARY

One embodiment of the invention is related to a method that can beperformed by a server computer. The method may comprise receiving a datapacket comprising a) recordable data and b) address data for a pluralityof electronic data storage processing modules run on one or morecomputers, the address data comprising a first address for a firstelectronic data storage processing module and a second address for asecond electronic data storage processing module. The method may furthercomprise routing the recordable data and at least some of the addressdata to the first electronic data storage processing module using thefirst address and processing the recordable data by the first electronicdata storage processing module. The method may further comprise routingthe recordable data processed by the first electronic data storageprocessing module to the second electronic data storage processingmodule using the second address and processing the recordable data bythe second electronic data storage processing module. The method mayfurther comprise recording the recordable data to an electronic datastorage of a plurality of different electronic data storages afterprocessing the recordable data by the second electronic data storageprocessing module. In some embodiments, the first electronic datastorage processing module comprises an aggregator module and the secondelectronic data storage processing module comprises a formatter module.

In some cases, processing the recordable data by the first electronicdata storage processing module may comprise determining a function fromthe aggregator module based on the first address and processing therecordable data using the function. The function may be configured toaggregate the recordable data.

In some cases, processing the recordable data by the second electronicdata storage processing module may comprise determining a function fromthe formatter module based on the second address processing therecordable data using the function. The function may be configured toformat the recordable data into a format compatible with the electronicdata storage.

In some embodiments, the method may comprise further steps wherein thedata packet may be a first data packet, the recordable data may be afirst recordable data, and the electronic data storage may be a firstelectronic data storage. The method may further comprise receiving asecond data packet comprising a) second recordable data and b) secondaddress data for the plurality of electronic data storage processingmodules run on the one or more computers, the address data comprisingthe first address for the first electronic data storage processingmodule and a third address for the second electronic data storageprocessing module. The method may further comprise routing, therecordable data and at least some of the address data to the firstelectronic data storage processing module using the first address andprocessing the recordable data by the first electronic data storageprocessing module. The method may further comprise routing therecordable data processed by the first electronic data storageprocessing module to the second electronic data storage processingmodule using the third address and processing the recordable data by thesecond electronic data storage processing module. The method may furthercomprise recording the recordable data to a second electronic datastorage of the plurality of different electronic data storages afterprocessing the recordable data by the second electronic data storageprocessing module.

In some embodiments, the function may be a first function and processingthe recordable data by the second electronic data storage processingmodule may comprise determining a second function from the formattermodule based on the third address and processing the recordable datausing the second function. The second function may be configured to intoa format compatible with the second electronic data storage.

In some implementations, at least some of the plurality of differentelectronic data storages may be in different formats and can be used forrecording different types of recordable data. For example, the differentelectronic data storage may be respectively adapted to record data forcryptocurrency transactions, non-financial asset ownership transactions,and identity verification transactions.

Another embodiment of invention is directed to a server computercomprising a processor and a computer readable medium coupled to theprocessor, the computer readable medium comprising code, executable bythe processor to implement a method. The method may comprise receiving adata packet comprising a) recordable data and b) address data for aplurality of electronic data storage processing modules run on one ormore computers, the address data comprising a first address for a firstelectronic data storage processing module and a second address for asecond electronic data storage processing module. The method may furthercomprise routing the recordable data and at least some of the addressdata to the first electronic data storage processing module using thefirst address and processing the recordable data by the first electronicdata storage processing module. The method may further comprise routingthe recordable data processed by the first electronic data storageprocessing module to the second electronic data storage processingmodule using the second address and processing the recordable data bythe second electronic data storage processing module. The method mayfurther comprise recording the recordable data to an electronic datastorage of a plurality of different electronic data storages afterprocessing the recordable data by the second electronic data storageprocessing module.

Another embodiment of invention is directed to a method that can beperformed by a user device. The method can comprise determining a datapacket comprising a) recordable data and b) address data for a pluralityof electronic data storage processing modules run on one or morecomputers, the address data comprising a first address for a firstelectronic data storage processing module and a second address for asecond electronic data storage processing module. The method can furthercomprise sending, to a server computer, the data packet with a requestto record the recordable data to an electronic data storage of aplurality of different electronic data storages. The method may furthercomprise receiving a confirmation that the recordable data was recordedto the electronic data storage. In some embodiments, the recordable datamay be routed to the first electronic data storage processing moduleusing the first address and processed by the first electronic datastorage processing module. Further, the recordable data is routed to thesecond electronic data storage processing module using the secondaddress and processed by the second electronic data storage processingmodule.

In some embodiments, the method may comprise further steps wherein thedata packet may be a first data packet, the recordable data may be firstrecordable data, the electronic data storage may be a first electronicdata storage, and the request may be a first request. The method mayfurther comprise determining a second data packet comprising a) secondrecordable data and b) address data for a plurality of electronic datastorage processing modules run on one or more computers. The addressdata may comprise the first address for the first electronic datastorage processing module and a third address for the second electronicdata storage processing module. The method may further comprise sending,to a server computer, the second data packet with a second request torecord the recordable data to a second electronic data storage of theplurality of different electronic data storages. The method may furthercomprise receiving a confirmation that the recordable data was recordedto the electronic data storage. In some cases, the second recordabledata may be routed to the first electronic data storage processingmodule using the first address and processed by the first electronicdata storage processing module, and the second recordable data may berouted to the second electronic data storage processing module using thethird address and processed by the second electronic data storageprocessing module.

Another embodiment of the invention is further directed to a user devicecomprising a processor and a memory element. The memory element cancomprise code, executable by the processor, for implementing a method.The method can comprise determining a data packet comprising a)recordable data and b) address data for a plurality of electronic datastorage processing modules run on one or more computers, the addressdata comprising a first address for a first electronic data storageprocessing module and a second address for a second electronic datastorage processing module. The method can further comprise sending, to aserver computer, the data packet with a request to record the recordabledata to an electronic data storage of a plurality of differentelectronic data storages. The method may further comprise receiving aconfirmation that the recordable data was recorded to the electronicdata storage. In some cases, the recordable data may be routed to thefirst electronic data storage processing module using the first addressand processed by the first electronic data storage processing module andthe recordable data may be routed to the second electronic data storageprocessing module using the second address and processed by the secondelectronic data storage processing module.

These and other embodiments of the invention are described in furtherdetail below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a block diagram showing various elements of an exemplarysystem according to embodiments of the present invention.

FIG. 2 shows a block diagram showing various elements of an exemplarysystem according to embodiments of the present invention.

FIG. 3 shows a block diagram showing various elements of an exemplarysystem according to embodiments of the present invention.

FIG. 4 shows a flow diagram of an exemplary process conducted by aserver computer according to embodiments of the present invention.

FIG. 5 shows a flow diagram of an exemplary process conducted by a userdevice according to embodiments of the present invention.

FIG. 6 shows a block diagram showing various elements of a servercomputer according to embodiments of the present invention.

FIG. 7 shows a block diagram showing various elements of a user deviceaccording to embodiments of the present invention.

DETAILED DESCRIPTION

Embodiments of the invention are directed to a system that enablesentities to access a single platform in order to utilize electronic datastorage for storing different types of information. One or morecomputers may operate a network that entities can access when updatinginformation in electronic data storage. The network may operate aplurality of electronic data storage processing modules, which caninclude an aggregator module, a formatter module, an operator signermodule, and a validator module. Based on the specific use case for whichelectronic data storage is utilized, recordable data that is to be addedto the electronic data storage can be processed by the appropriateaggregating, formatting, signing, and validating functions provided bythe electronic data storage processing modules.

Before discussing specific embodiments and examples, some descriptionsof terms used herein are provided below.

“Electronic data storage” may refer to a compilation of data. Theelectronic data storage may include entries with information related toevents, messages, or transactions. The electronic data storage maycomprise a database or other comparable data structure that may beconfigured to store data from all previous entries. In some cases, eachentry may include a timestamp of the corresponding event (e.g.,transmission of message, conducting a transaction, transfer ofownership, etc.) as well as information related to entities involved(e.g., the sender and the receiver of a message, the requestor andresource provider of a transaction, the entities to and from whichownership is transferred, etc.). In some embodiments, the electronicdata storage may be in the form of an electronic ledger (e.g.,blockchain) in which data already stored in the electronic data storageis unalterable. In some embodiments, some or all entities within asystem may store their own copies of information in one or moreelectronic data storages.

“Recordable data” may refer to information that can be recorded. In somecases, recordable data may be information that can be stored inelectronic data storage. In some embodiments, recordable data mayinclude information related to an event (e.g., transmission of message,conducting a transaction, transfer of ownership, etc.). For example,recordable data may include information indicating a date and time(e.g., timestamp), entities involved in an event (e.g., identifierscorresponding to the sender and the receiver of a message, the requestorand resource provider of a transaction, the entities to and from whichownership is transferred, etc.), and other characteristics of an event(e.g., location information, reason for request, requested resource,transaction amount, transaction data, etc.).

“Transaction data” (which may also be known as transaction information)may refer to any data or information surrounding or related to atransaction. For example, transaction data may include transactiondetails and any data associated with the transaction that may beutilized by entities involved in the transaction process. For instance,the transaction data may include information useful for processingand/or verifying the transaction. Transaction data may also include anydata or information surrounding or related to any participants partakingin or associated with the transaction. Example transaction data mayinclude a transaction amount, transaction location, resources received(e.g., products, documents, etc.), information about the resourcesreceived (e.g., size, amount, type, etc.), resource providing entitydata (e.g., merchant data, document owner data, etc.), user data, dateand time of a transaction, payment method, and other relevantinformation.

“Address data” may refer to information that indicates a particularlocation. In some embodiments, the address data may include informationthat indicates a location within electronic data storage or memory in acomputer. For example, the address data may include a unique number thatrefers to a certain byte of data stored in memory. In some cases, theaddress data may indicate electronic data storage processing module towhich recordable data should be routed.

“Electronic data storage processing modules” may refer to code that canbe utilized to process information related to an electronic datastorage. In some cases, electronic data storage processing module mayinclude code and other data that can enable various types of processing,such as aggregating, formatting, signing, or validating informationrelated to an electronic data storage. In some embodiments, eachelectronic data storage processing module may include code correspondingto a plurality of functions that can process information related to anelectronic data storage. An exemplary electronic data storage processingmodule may be a formatter processor module, which may include codecorresponding to a plurality of formatting functions that can formatinformation related to an electronic data storage.

A “digital signature” may refer to an electronic signature. In someembodiments, the digital signature may be used to validate theauthenticity of information (e.g., message) sent within a system. Adigital signature may be a unique value generated based on theinformation and a private key using an encryption algorithm. In someembodiments, a verification algorithm using a public key may be used toverify the digital signature. The digital signature may be a numericvalue, an alphanumeric value, or any other type of data including agraphical representation.

A “key” may refer to a piece of data or information used for analgorithm. A key may be a unique piece of data. In some cases, the keymay be an asymmetric key that is typically part of a key pair, where afirst key may be utilized to encrypt data and a second key may beutilized to decrypt the encrypted data. In other cases, the key may be asymmetric that can be utilized to encrypt data and also decrypt theencrypted data. The key may be a numeric or alphanumeric value and maybe generated using an algorithm.

A “resource providing entity” may be an entity that may make resourcesavailable to a user. Resource providing entities may also be known asresource providers. Examples of resource providing entities includemerchants, vendors, suppliers, owners, traders, wallet providers,service providers, and the like. In some embodiments, such entities maybe a single individual, small groups of individuals, or larger groups ofindividuals (e.g., companies). Resource providing entities may beassociated with one or more physical locations (e.g., supermarkets,malls, stores, etc.) and online platforms (e.g., e-commerce websites,online companies, etc.). In some embodiments, resource providingentities may make available resources that are physical items (e.g.,goods, products, etc.) to the user. In other embodiments, resourceproviding entities may make available digital resources (e.g.,electronic documents, electronic files, etc.) or services (e.g., digitalwallet services) to the user. In some embodiments, resource providingentities may manage access to certain resources by the user.

An “authorization computer” can include any system enabling anauthorization process. The authorization computer may determine whethera transaction can be authorized and may generate an authorizationresponse message including an authorization status (also may be known asan authorization decision). In some embodiments, an authorizationcomputer may be an issuer computer that issues accounts (e.g., paymentaccounts) and corresponding account information to users. In some cases,the authorization computer may store contact information of one or moreusers.

A “server computer” can be a powerful computer or a cluster ofcomputers. For example, the server computer can be a large mainframe, aminicomputer cluster, or a group of servers functioning as a unit. Inone example, the server computer may be a database server coupled to aWeb server.

FIG. 1 illustrates an exemplary system 100 with at least some of thecomponents for implementing embodiments of the invention. System 100 mayenable entities to access a network to update information of a pluralityof electronic data storage, where at least some of the plurality ofelectronic data storage may be utilized for recording different type ofrecordable data. FIG. 1 includes a wearable device 101, a mobile device102, and a motor vehicle 103 in communication with an electronic datastorage processing network 150. Electronic data storage processingnetwork 150 may be operated by server computers 151 to 155 and mayprocess recordable data that can be added to an electronic data storage110, 120, and 130.

Each of the computing devices (e.g., wearable device 101, mobile device102, and motor vehicle 103, server computers 151-155) in FIG. 1 mayinclude a network interface and may be capable of communicating (e.g.,remotely) with each other or other computing devices over acommunications network (e.g., electronic data storage processing network150). Further, each of the computing devices may include a processor anda computer readable medium comprising code, executable by the processorfor performing the functionality described herein. Each of the computingdevices in FIG. 1 may also be capable of short-range communicationthrough contact or contactless methods (e.g., NFC, Wi-Fi, Bluetooth,etc.).

While system 100 shows three exemplary user devices accessing electronicdata storage processing network 150, embodiments are not so limiting. Inother embodiments, there may be more than three user devices or fewerthan three computing devices accessing electronic data storageprocessing network 150. Further, in some embodiments, other types ofuser devices may be part of system 100 instead of or in addition towearable device 101, mobile device 102, and motor vehicle 103. Somenon-limiting examples of such user devices include cellular phones,keychain devices, personal digital assistants (PDAs), notebooks,laptops, notepads, smart watches, fitness bands, jewelry, automobileswith remote communication capabilities, personal computers, cards (e.g.,smart cards, magnetic stripe cards, etc.), and the like.

Each of the user devices in FIG. 1 may be operated by a user. In somecases, the same user may operate more than one of the user devices. Inother cases, a different user may operate each of the computing devices.A user may be an individual or an entity represented by a group ofindividuals (e.g., corporation, etc.). In some cases, a user may be ableto input information into wearable device 101, mobile device 102, ormotor vehicle 103. In some embodiments, the user may input informationinto the user device using a user interface provided by a mobileapplication.

Electronic data storage processing network 150 may comprise a pluralityof networks for secure communication of data and information betweenentities. In some embodiments, electronic data storage processingnetwork 150 may follow a suitable communication protocol to generate oneor more secure communication channels. A communication channel may insome instances comprise a “secure communication channel,” which may beestablished in any known manner, including the use of mutualauthentication and a session key and establishment of an SSL session.However, any method of creating a secure channel may be used. Byestablishing a secure channel, sensitive information may be securelytransmitted.

Any suitable communications protocol may be used for generating acommunications channel. Suitable communications networks may be any oneand/or the combination of the following: a direct interconnection; theInternet; a Local Area Network (LAN); a Metropolitan Area Network (MAN);an Operating Missions as Nodes on the Internet (OMNI); a secured customconnection; a Wide Area Network (WAN); a wireless network (e.g.,employing protocols such as, but not limited to a Wireless ApplicationProtocol (WAP), I-mode, and/or the like); and/or the like.

Messages between the computers, networks, and devices described hereinmay be transmitted using a secure communications protocols such as, butnot limited to, File Transfer Protocol (FTP); HyperText TransferProtocol (HTTP); Secure Hypertext Transfer Protocol (HTTPS), SecureSocket Layer (SSL), ISO (e.g., ISO 8583) and/or the like.

In some embodiments, electronic data storage processing network 150 maybe operated by server computers 151-155 that enable electronic datastorage processing capabilities. In some cases, the electronic datastorage processing capabilities may include aggregating, formatting,signing, and validating of recordable data that is to be recorded inelectronic data storage. Server computers 151-155 may enable electronicdata storage processing capabilities for a plurality of differentelectronic data storages that are in different formats and that are usedfor recording different types of recordable data. For example,recordable data from wearable device 101, mobile device 102, and motorvehicle 103 may each relate to different types of transactions and mayall processed by electronic data storage processing network 150.

Electronic data storage processing network 150 may process recordabledata from wearable device 101, which may be utilized to conduct identityverification transactions. An identity verification transaction maycomprise a process in which information associated with the identity ofa user associated a device or the device itself is verified. When anidentity verification transaction is conducted by wearable device 101,one or more server computers 151-155 may process recordable data relatedto the identity verification transaction. The one or more servercomputers 151-155 perform processing that is specific to identityverification transactions. For example, relevant information (e.g., datafields) may be extracted from the recordable data and formatted into aformat that is compatible with electronic data storage 110, which canrecord recordable data related to identity verification transactions.

Electronic data storage processing network 150 may also processrecordable data from mobile device 102, which may be utilized to conductcryptocurrency transactions. A cryptocurrency transaction may comprise aprocess in which a resource is requested by a requestor in exchange forcryptocurrency. When a cryptocurrency transaction is conducted by mobiledevice 102, one or more server computers 151-155 may process recordabledata related to the cryptocurrency transaction. The one or more servercomputers 151-155 perform processing that is specific to cryptocurrencytransactions. For example, relevant information (e.g., data fields) maybe extracted from the recordable data and formatted into a format thatis compatible with electronic data storage 120, which can recordrecordable data related to cryptocurrency transactions

Additionally, electronic data storage processing network 150 may processrecordable data from motor vehicle 103, which may be utilized to conductownership transactions. An ownership transaction may comprise a processin which ownership of an asset, which can be a non-financial asset, istransferred form one owner to another owner. When an ownershiptransaction is conducted by motor vehicle 103, one or more servercomputers 151-155 may process recordable data related to the ownershiptransaction. The one or more server computers 151-155 perform processingthat is specific to ownership transactions. For example, relevantinformation (e.g., data fields) may be extracted from the recordabledata and formatted into a format that is compatible with electronic datastorage 130, which can record recordable data related to ownershiptransactions.

Embodiments of the invention are advantageous over conventional systems,which typically include multiple disconnected modules for processingdifferent types of recordable data. In a conventional system, if anentity wants to utilize different electronic data storage to storeinformation related to different types of transactions, the entitytypically has to onboard with multiple platforms that provide processingcapabilities for the different types of transactions. For example, theentity may have to register with a platform specifically for recordinginformation related to cryptocurrency transactions, as well as withanother platform specifically for recording information related toownership transactions. In contrast, in embodiments of the invention,electronic data storage processing network 150 can provide a singleplatform that enables processing of a plurality of different types ofrecordable data that is to be recorded in electronic data storage. Thisreduces use of computing resources and processing power typicallyutilized to register and communicate with multiple electronic datastorage platforms.

It is understood that FIG. 1 depicts an exemplary system and that thecomponents shown in system 100 are not limiting. For example, in somecases, more or fewer than five server computers may operate electronicdata storage processing network 150. Additionally, in some cases, theremay be more or fewer than three electronic data storage that can recordrecordable data processed by electronic data storage processing network150.

FIG. 2 illustrates an exemplary system 200 with at least some of thecomponents for implementing embodiments of the invention. FIG. 2 depictsdata 201-203 related to transactions conducted by user devices 204-206in communication with reader devices 207-209. FIG. 2 also depicts fourelectronic data storage processing modules, which include an aggregatormodule 210, a formatter module 211, an operator signer module 212, and avalidator module 213. The electronic data storage processing modules maymake up a electronic data storage processing network and in some casesmay be operated by one or more server computers (not shown). FIG. 2 alsoshows electronic data storage 220, 230, 240, which may be utilized torecord data that is processed by the electronic data storage processingmodules.

User devices 204-206 may be any suitable computing devices operated by auser. User devices 204-206 may be capable of conducting electronictransactions. In some embodiments, user devices 204-206 may includesimilar characteristics to those described for user devices (e.g.,wearable device 101, mobile device 102, or motor vehicle 103) withrespect to FIG. 1. In some embodiments, one or more of user devices204-206 may be operated by the same user.

Reader devices 207-209 may be any suitable computing devices that cancommunicate information to and from other computing devices. In thisexemplary case, reader devices 207-209 may receive information from userdevices 204-206, respectively. In some embodiments, reader devices207-209 may receive information from user devices 204-206 remotely overa communications network. In other embodiments, reader devices 207-209may receive information from user devices 204-206 over short-rangecommunication through contact or contactless methods (e.g., NFC, Wi-Fi,Bluetooth, etc.). In some cases, reader device 207 may be operated by anentity with which user device 204 is conducting a transaction.Additionally, reader device 208 may be operated by an entity with whichuser device 205 is conducting a transaction and reader device 209 may beoperated by an entity with which user device 206 is conducting atransaction. Some non-limiting examples of such reader devices includetablets, notebooks, laptops, notepads, personal computers, mobilephones, server computers, point-of sale terminal devices, and the like.

Data 201-203 may include information associated with transactions. Eachof data 201-203 may comprise recordable data that may includeinformation related to a transaction conducted by user devices 204-206,respectively. For example, the recordable data may include informationindicating a date and time (e.g., timestamp) of a transaction, entitiesinvolved in a transaction (e.g., identifiers corresponding to the senderand the receiver of a message, the requestor and resource provider of atransaction, the entities to and from which ownership is transferred,etc.), and other characteristics of an transaction (e.g., locationinformation, reason for request, requested resource, transaction amount,transaction data, etc.).

Electronic data storage 220-240 may store recordable data processed byone or more electronic data storage processing modules. In someembodiments, each of electronic data storage 220-240 may store dataentries associated with a plurality of transactions. Each of the dataentries may include recordable data. In some implementation, electronicdata storage 220-240 may be configured so that data that is alreadystored is unalterable.

For example, electronic data storage 220 may be in the form of ablockchain and recordable data corresponding to a new transaction can bestored in a new entry. The new entry may also comprise a data headerthat includes information that makes the new entry unalterable withoutdetection. For example, the data header may include a hash of theprevious entry in electronic data storage 220, as well as a root valuecomputed based on all past entries in electronic data storage. Sinceeach entry in electronic data storage 220 may be generated in a similarmanner by including a data header storing information referencing itsprevious entries, no data already stored in electronic data storage 220can be modified without affecting all following entries. This can ensurethat any tampering of stored information, such as an attempt to reassignan asset to an inappropriate entity, will not go unnoticed. Electronicdata storage 230 and 240 may include similar characteristics to thosedescribed for electronic data storage 220.

While electronic data storage 220-240 can include some structuralsimilarities with each other as described above, electronic data storage220-240 may be utilized for recording information associated withdifferent types of transactions. Different types of transactions cangenerate various types of recordable data due to differences in thetypes of originating devices, messaging protocols, message formats, andother factors. As a result, uniform processing cannot be performed onthe various types of recordable data before being recorded in electronicdata storage. The utilization of electronic data storage processingmodules shown in FIG. 2 enable an efficient method for handling avariety of processing for different types of recordable data.

Aggregator module 210 may include software that enables aggregation ofrecordable data. Aggregator module 210 may receive and combinerecordable data from one or more sources. For example, in some cases,aggregator module 210 may aggregate recordable data corresponding to oneor more transactions. In an exemplary case, aggregator module 210 mayaggregate recordable data corresponding to ten transactions processed byreader device 207, one or more of which may have been conducted by userdevice 204. In other embodiments, aggregator module 210 may simplyaggregate recordable data for a single transaction into a data packet.Aggregator module 210 may also provide aggregated recordable data toformatter module 211.

In some embodiments, aggregator module 210 may include a plurality ofaggregating functions, shown as functions A1, A2, and A3 in FIG. 2. Eachaggregating function may include code for aggregating recordable data.Each aggregating function may be associated with an address that can beutilized to identify the aggregating function. In some embodiments, someof the aggregating functions may be the same function, in which casethey may be associated with the same address.

Formatter module 211 may include software that enables formatting ofrecordable data. Formatter module 211 may receive recordable datacorresponding to one or more transactions from aggregator module 210.Formatter module 211 may enable extraction of relevant information fromthe recordable data and formatting of the extracted information into aformat that is compatible for storage into an electronic data storage.In some cases, formatter module 211 may enable determination of valuesof certain data fields in a received message based on the format of themessage (e.g., HTTP, ISO, XML, etc.). For example, if the receivedmessage is an HTTP message, formatter module 211 may be able todetermine which data fields, based on an HTTP message standard, includerelevant information that is to be recorded in electronic data storageand then extract values from those data fields. Formatter module 211 maythen convert the determined values so that they are compatible with thespecifications of electronic data storage. For example, formatter module211 may convert any of the determined values as appropriate to becompatible with these characteristics field length or character typespecifications of data fields of the electronic data storage. Formattermodule 211 may also provide the recordable data that has been convertedto appropriate format to operator signer module 212.

In some embodiments, formatter module 211 may include a plurality offormatting functions, shown as functions F1, F2, and F3 in FIG. 2. Eachformatting function may include code for formatting a certain type ofrecordable data. Each formatting function may be associated with anaddress that can be utilized to identify the formatting function. Insome embodiments, some of the formatting functions may be the samefunction, in which case they may be associated with the same address.

Operator signer module 212 may include software that enables digitalsigning of recordable data. Operator signer module 212 may receiverecordable data from formatter module 211. In some cases, operatorsigner module 212 may enable determination of an appropriate operatingentity to digitally sign the recordable data and then provide therecordable data to the operating entity, which can digitally sign therecordable data using their private key to produce a digital signature.In some embodiments, the digital signature may be utilized as proof thatthe recordable data was processed by a trusted entity before beingrecorded to an electronic data storage. Operator signer module 212 mayalso provide the recordable data along with the digital signature tovalidator module 213.

In some embodiments, operator signer module 212 may include a pluralityof signing functions, shown as functions S1, S2, and S3 in FIG. 2. Eachsigning function may include code for digitally signing recordable data.Each signing function may be associated with an address that can beutilized to identify the signing function. In some embodiments, some ofthe signing functions may be the same function, in which case they maybe associated with the same address.

Validator module 213 may include software that enables validation ofrecordable data. Validator module 213 may receive the recordable dataalong with the digital signature from operator signer module 212. Insome cases, validator module 213 may enable one or more validatingentities to validate the recordable data and/or the digital signature.The recordable data can be validated based on a series of verificationprocesses, which may be specific to the type of electronic data storageinto which the recordable data is to be recorded. In some cases, theverification processes can include one or more of verifying that theformat of the recordable data is valid, verifying a timestamp associatedwith the recordable data is valid (e.g., not expired), verifying thedigital signature provided by operator signer module 212 using thecorresponding public key of the operating entity, as well as verifyingany other digital signatures that may be include in the recordable data.In some cases, if the one or more validating entities determine that therecordable data is valid, the one or more validating entities maydigitally sign the recordable data with their corresponding public key.Validator module 213 may record the recordable data along with thedigital signatures in electronic data storage.

In some embodiments, validator module 213 may include a plurality ofvalidating functions, shown as functions V1, V2, and V3 in FIG. 2. Eachvalidating function may include code or data for validating recordabledata. Each validating function may be associated with an address thatcan be utilized to identify the validating function. In someembodiments, some of the validating functions may be the same function,in which case they may be associated with the same address.

An exemplary process is described below with respect to some componentsshown in system 200. Some steps are described with respect to FIG. 4,which depicts a flow 300 according to embodiments of the invention. Flow300 may be performed by a server computer, which may operate electronicdata storage processing modules 210-213. Additionally, some steps aredescribed with respect to FIG. 5, which depicts a flow 400 according toembodiments of the invention.

In an exemplary case, user device 204 may communicate (e.g., remotely orover short-range wireless connection) with reader device 207 to conductan ownership transaction, in which ownership of an asset is transferredfrom one owner to another owner. The asset may be any suitable propertythat can be owned, such as a car, a house, or jewelry. Reader device 207may be associated with an entity with which user device 204 conducts thetransaction, such as an ownership transfer service provider.

Upon communication between user device 204 and reader device 207, data201 may be generated. Data 201 may include any recordable data that canindicate the transfer in ownership of the asset, such as informationindicating a date and time (e.g., timestamp) of the ownership transfer,entities involved in the ownership transfer (e.g., identifierscorresponding to the original owner and the new owner, etc.), and othercharacteristics of the ownership transfer (e.g., details about theasset, location information, reason for ownership transfer, etc.). Data201 may be generated by one or more of user device 204 and the ownershiptransfer service provider.

In some cases, user device 204 may determine a data packet includingdata 201, as well as address data for a plurality of electronic datastorage processing modules run on one or more computers (step S401). Theaddress data may comprise a plurality of addresses corresponding to aplurality of electronic data storage processing modules. For example,the address data may comprise a first address for a first electronicdata storage processing module and a second address for a secondelectronic data storage processing module.

In some embodiments, the address data may indicate an order associatedwith the plurality of addresses. For example, in some cases, thesequence in which the plurality of addresses are included in the addressdata may correspond to the order of electronic data storage processingmodules to which the recordable data is to be routed. In other cases,the address data may include sequence identifiers that indicate theorder in which the plurality of addresses is to be utilized for routingthe recordable data to an electronic data storage processing modules.

User device 204 may send the data packet to reader device 207 along witha request to record the recordable data to an electronic data storage ofa plurality of different electronic data storages (step S402). In thisexemplary case, the electronic data storage to which user device 204requests that the recordable data be recorded may be electronic datastorage 240, which may specifically be for recording ownershiptransactions. Thus, electronic data storage 240 may store differenttypes of recordable data compared to at least some of the plurality ofdifferent electronic data storages (e.g., electronic data storage 220,electronic data storage 230, etc.).

Reader device 207 may then provide the data packet comprising data 201and the address data to a server computer operating an electronic datastorage processing network. The electronic data storage processingnetwork may enable a plurality of electronic data storage processingmodules including aggregator module 210, formatter module 211, operatorsigner module 212, and validator module 213. Upon receiving the datapacket (step S301), the server computer may process the address data.

The server computer may determine the first address included in theaddress data. In some cases, the server computer may determine the firstaddress by extracting a predetermined number of bits from the addressdata. In some implementations, the server computer may extract theleftmost bits of the address data to determine the first address. Inother cases, the server computer may determine the first address basedon sequence identifiers in the address data that indicate the order ofthe plurality of addresses. For example, the server computer maydetermine that the address associated with a sequence identifier of “1”is the first address.

The server computer may route the recordable data and at least some ofthe address data to the first electronic data storage processing moduleusing the first address (step S602). In some embodiments, the firstaddress may indicate a location in memory that stores information withinthe first electronic data storage processing module for processing therecordable data. In this exemplary case, the first electronic datastorage processing module may comprise an aggregator module 210 and thefirst address may correspond to an aggregating function A1 foraggregating recordable data. Accordingly, the server computer may routethe recordable data and at least some of the address data to aggregatingfunction A1 of aggregator module 210.

The server computer may then process the recordable data by the firstelectronic data storage processing module (step S303). For example,processing the recordable data by the first electronic data storageprocessing module may comprise calling aggregating function A1 with therecordable data as an input. Aggregating function A1 may enablecombining the received recordable data with other recordable datacorresponding to other transactions. For example, aggregating functionA1 may enable combining of the received recordable data with otherrecordable data corresponding to other ownership transactions.

In some cases, aggregating function A1 may send a request to anaggregator device to perform the aggregation. Upon performing theaggregation, the aggregator device can then return the aggregated resultback to the server computer. In some embodiments, the aggregator devicemay be the server computer while in other embodiments, the aggregatordevice may be a separate computing device.

After the first electronic data storage processing module processes therecordable data, the server computer may then determine the secondaddress included in the address data. In some cases, the server computermay determine the second address by extracting a predetermined number ofbits from the address data. In some implementations, the server computermay extract leftmost bits of the address data following the firstaddress to determine the second address. In other cases, the servercomputer may determine the second address based on sequence identifiersin the address data that indicate the order of the plurality ofaddresses. For example, the server computer may determine that theaddress associated with a sequence identifier of “2” is the secondaddress.

The server computer may route the recordable data processed by the firstelectronic data storage processing module to a second electronic datastorage processing module using the second address (step S304). In someembodiments, the second address may indicate a location in memory thatstores information within the second electronic data storage processingmodule for processing the recordable data. In this exemplary case, thesecond electronic data storage processing module may comprise aformatter module 211 and the second address may correspond to anformatting function F2 for formatting the recordable data. Accordingly,the server computer may route the recordable data to formatting functionF2 of formatter module 211.

The server computer may then process the recordable data by the secondelectronic data storage processing module (step S305). For example,processing the recordable data by the second electronic data storageprocessing module may comprise calling formatting function F2 offormatter module 211 with the recordable data as an input. Formattingfunction F2 may enable the received recordable data to be formatted tobe compatible with electronic data storage 240 to which user device 204requested that the recordable data be recorded.

In this exemplary case, the recordable data may include a payload of anHTTP message and thus formatting function F2 may enable a conversion ofthe recordable data from a HTTP format to a format compatible with theelectronic data storage indicated by user device 204. Formattingfunction F2 may enable determination of which data fields, based on anHTTP message standard, include relevant information that is to berecorded in electronic data storage 240. For example, formattingfunction F2 may determine the data fields in the recordable datacorresponding to information indicating a date and time (e.g.,timestamp) of the ownership transfer, entities involved in the ownershiptransfer (e.g., identifiers corresponding to the original owner and thenew owner, etc.), and other characteristics of the ownership transfer(e.g., details about the asset, location information, reason forownership transfer, etc.). Formatting function F2 may then enableextraction of these data field values from the recordable data.Formatting function F2 may include the determined values into a dataentry in a way that is compatible with the specifications of electronicdata storage 240. For example, formatting function F2 may convert any ofthe determined values as appropriate to be compatible with field lengthor character type specifications for data entries of electronic datastorage 240.

In some cases, formatting function F2 may send a request to a formatterdevice to perform the formatting. Upon performing the formatting, theformatter device can then return the formatted result back to the servercomputer. In some embodiments, the formatter device may be the servercomputer while in other embodiments, the formatter device may be aseparate computing device.

In some embodiments, the recordable data may be further routed andprocessed by other electronic data storage processing modules beforebeing recorded to an electronic data storage 240. For example, therecordable data formatted by formatter module 211 may be routed to andprocessed by function S2 of operator signer module 212, which may enablethe recordable data to be digitally signed to produce a digitalsignature. In addition, the recordable data along with the digitalsignature may be routed to an processed by function V3 of validatormodule 213, which may enable the recordable data to be validated beforebeing recorded to an electronic data storage 240.

The recordable data may be routed to operator signer module 212 andvalidator module 213 based on addresses in the recordable data. Forexample, the server computer may route the recordable data to operatorsigner module 212 using a third address. The server computer maydetermine the third address from the address data, where the thirdaddress may correspond to function S2 of operator signer module 212.Additionally, the server computer may route the recordable data tovalidator module 213 using a fourth address. The server computer maydetermine the fourth address from the address data, where the fourthaddress may correspond to function V3 of validator module 213.

After the recordable data has been processed by the second electronicdata storage processing module and in some cases as well as by otherelectronic data storage processing modules, the server computer mayrecord the recordable data to an electronic data storage 240 (stepS306). In some embodiments, the recordable data may be recorded to anelectronic data storage 240 by including the recordable data formattedby formatter module 211 into a new data entry of electronic data storage240. In some embodiments, the data entry may be stored in electronicdata storage 240 in association with electronic data storage account ofthe user operating user device 204. In this case, the data entry may bestored in associated with the public address (e.g., hashed public key)associated with the user of user device 204 to indicate that the userconducted the ownership transaction.

In some embodiments, the data entry may include additional data. Forexample, the data entry may also include one or more digital signaturesthat may be generated by one or more of user device 204, operator signermodule 212, or validator module 213, where the digital signatures canindicate that that recordable data was processed by authenticatedentities. In some cases, the data entry may also comprise a data headerthat includes information that makes the new entry unalterable withoutdetection. For example, the data header may include a hash of theprevious entry in electronic data storage 240, as well as a root valuecomputed based on all past entries in electronic data storage 240. Sinceeach entry of electronic data storage 240 may be generated in a similarmanner by including a data header storing information referencing itsprevious entries, no data already stored in electronic data storage 240can be modified without affecting all following entries. This can ensurethat any tampering of stored information, such as an attempt to reassignan asset to an inappropriate entity, will not go unnoticed.

In some embodiments, the server computer may send user device 204 aconfirmation that the recordable data was successfully recorded to anelectronic data storage 240. User device 204 may receive theconfirmation that the recordable data was recorded to an electronic datastorage 240 (step S403), which can indicate the completion of thetransaction. In this exemplary case, the completion of the ownershiptransaction may result in proof stored in electronic data storage 240that the ownership of the asset being successfully transferred from theoriginal owner to the new owner.

While utilization of an exemplary combination of electronic data storageprocessing functions including aggregating function A1, formattingfunction F2, signing function S2, and validating function V3 isdescribed above, it is understood that any other suitable combinationsof electronic data storage processing functions may be utilized. Forexample, FIG. 2 also shows an exemplary combination of electronic datastorage processing functions including aggregating function A2,formatting function F1, signing function S3, and validating function V2.FIG. 2 further shows another exemplary combination of electronic datastorage processing functions including aggregating function A3,formatting function F3, signing function S1, and validating function V1.

FIG. 3 shows use of further exemplary combinations of electronic datastorage processing functions. As shown in FIG. 3, some functions may notbe utilized. Additionally, in some cases, recordable data for differenttransactions can be processed using some of the same electronic datastorage processing functions. While FIG. 3 includes only some of thecomponents shown in and described with respect to FIG. 2, it isunderstood that FIG. 3 can include additional components that are notexplicitly shown.

FIG. 3 shows two exemplary transactions being processed. A firsttransaction may be conducted and processed in a manner similar to thatdescribed with respect to FIG. 2. For example, data 201 may correspondto a first transaction that may be conducted between user device 204 andreader device 207. First recordable data of data 201 may be processedusing aggregating function A1, formatting function F2, signing functionS2, and validating function V3, as well as stored in electronic datastorage 240. In addition, data 202 may correspond to a secondtransaction that may be conducted between user device 205 and readerdevice 208. Second recordable data of data 202 may be processed using adifferent combination of electronic data storage processing functions asdescribed in further detail below. The combination of electronic datastorage processing functions for the first recordable data correspondingto the first transaction is depicted in FIG. 3 as a dashed line, whilethe combination of electronic data storage processing functions for thesecond recordable data corresponding to the second transaction isdepicted in FIG. 3 as a solid line.

For the second transaction, a server computer may receive a second datapacket comprising the second recordable data associated with the secondtransaction as well as second address data for the plurality ofelectronic data storage processing modules run on the one or morecomputers. The second address data may include the first address thatwas also included in the first address data for processing the firstrecordable data for the first transaction conducted by user device 204.This is because in this exemplary case, the first recordable data forthe first transaction and the second recordable data for the secondtransaction may be processed using the same aggregating function A1. Theserver computer may thus utilize the first address to route the secondrecordable data to aggregating function A1 of aggregator module 210,which can then process the second recordable data. Additionally, thesecond address data may also include another address that can utilizedto route the second recordable data to formatting function F1 offormatter module 211, which can the process the second recordable data.Formatting function F1 may convert the second recordable data into asecond format that is compatible with electronic data storage 230. Thesecond recordable data can additionally be routed to, based on twoadditional addresses in the second address data, and processed bysigning function S3 of operator signer module 212 and validatingfunction V2 of validator module 213. The second recordable data may thenbe recorded to electronic data storage 230.

Embodiments of the invention are advantageous over conventional systems,which typically include multiple disconnected modules for processingdifferent types of recordable data. In a conventional system, if anentity wants to utilize different electronic data storage to storeinformation related to different types of transactions, the entitytypically has to onboard with multiple platforms that provide processingcapabilities for the different types of transactions. For example, theentity may have to register with a platform specifically for recordinginformation related to cryptocurrency transactions, as well as withanother platform specifically for recording information related toownership transactions.

In contrast, embodiments of the invention can provide a single platformthat enables processing of a plurality of different types of recordabledata to be recorded in electronic data storage. For example, a user thatcan own multiple user devices that may each be utilized to conductdifferent types of transactions (e.g., identity verificationtransactions, cryptocurrency transactions, and ownership transactions).As a result, information associated with the different types oftransactions may have different types of recordable data be meant to berecorded in different electronic data storage. While conventionalsystems may require the user to onboard with a different electronic datastorage platform for each user device, embodiments of the invention canenable the user to onboard with a single electronic data storageplatform capable of processing multiple different types of recordabledata. This reduces use of computing resources and processing powertypically utilized to register and communicate with multiple electronicdata storage platforms.

FIG. 6 shows a block diagram of an exemplary server computer 500according to embodiments of the invention. FIG. 6 shows a number ofcomponents, and server computer 500 according to embodiments of theinvention may comprise any suitable combination or subset of suchcomponents. Server computer 500 includes a data processor 510 forexecuting functions, a network interface 520 for communicating withother computing devices, and a computer readable medium 530 for storingdata. The computer readable medium 530 may comprise a number of softwaremodules including a data packet processing engine 540, which cancomprise a routing module 541, a processing module 542, and a recordingmodule 543.

Other modules and submodules may also reside on computer readable medium530. Examples of additional modules may data extraction (e.g., forretrieving data from external data sources such as databases) modules,storage modules, and message modification modules. Each module residingon computer readable medium 530 may be combined with any of theadditional modules as appropriate. Any of the modules may comprise oneor submodules, where each submodule may comprise one or more functionsimplemented by code, executable by data processor 510.

In some embodiments, server computer 500 may also be in communicationwith several databases including address database 550, recordable dataformat database 560, and electronic data storage processing API 570.Each database may be a conventional, fault tolerant, relational,scalable, secure database such as those commercially available fromOracle™ or Sybase™. In some embodiments, any of the databases may becombined into a single database, or may be separated into multipledatabases. Server computer 500 may also be in communication with otherdatabases that are not shown in FIG. 6.

Routing module 541 may enable, with data processor 510, recordable datato be routed to appropriate electronic data storage processing modules.Routing module 541 may enable, with data processor 510, determination ofthe address data included in a data packet as well as determination of aplurality of addresses included in the address data. In someembodiments, routing module 541 may determine, with data processor 510,the plurality of addresses by splitting the address data based on theknown length of each address. In some cases, routing module 541 maydetermine, in conjunction with data processor 510, the sequence in whichthe plurality of addresses is to be utilized for routing to anelectronic data storage processing modules based on the relative orderof the addresses in the address data. In other cases, routing module 541may determine, in conjunction with data processor 510, the sequence inwhich the plurality of addresses is to be utilized for routing to anelectronic data storage processing modules based on sequence identifiersincluded in the address data. Each address in the address data may beassociated with a different sequence identifier, which can indicate arelative order in which the address is to be utilized.

Upon determining an address from the address data, routing module 541may enable, in conjunction with data processor 510, determination ofelectronic data storage processing module to which the recordable datashould be routed. In some embodiments, routing module 541 may accessaddress database 550 to determine the appropriate electronic datastorage processing module. For example, routing module 541 may query,with data processor 510, address database 550 with the determinedaddress. In response to the query, address database 550 may return afunction identifier (e.g., function name) in electronic data storageprocessing module that corresponds to the address. Routing module 541may send, using data processor 510, the function identifier toprocessing module 542.

Processing module 542 may enable, with data processor 510, recordabledata to be processed by electronic data storage processing modules. Uponreceiving a function identifier, processing module 542 may call, inconjunction with data processor 510, the function using information inelectronic data storage processing API 570. In some embodiments,processing module 542 may query, with data processor 510, electronicdata storage processing API 570 using the function identifier (e.g.,function name) received from routing module 541 in order to determineinformation related to the function. In some cases, the informationrelated to the function may indicate the number of arguments of thefunction, the type of arguments of the function, the electronic datastorage processing function associated with the function, and any othersuitable information that can be utilized to call the function.

In some embodiments, processing module 542 may access, with dataprocessor 510, recordable data format database 560 for processingrecordable data. For example, this may occur when the function to becalled is associated with electronic data storage processing module forformatting recordable data (e.g., formatter module). The function mayenable conversion of recordable data into a format compatible withelectronic data storage. In some embodiments, processing module 542 mayaccess, with data processor 510, recordable data format database 560using the function identifier associated with the function. By accessingrecordable data format database 560, processing module 452 maydetermine, with data processor 510, information related to the format ofthe recordable data from which as well the format of the electronic datastorage to which the function is meant to perform the conversion. Thisinformation may include the order, lengths, as well as types of datafields in the recordable data and in a data entry of the electronic datastorage. Additionally, the information may indicate a mapping betweendata fields in the recordable data and data fields in the electronicdata storage. Processing module 542 may then determine, in conjunctionwith data processor 510, convert values of data fields from therecordable data to values of corresponding data fields in the electronicdata storage according to the information determined from recordabledata format database 560.

Recording module 543 may enable, in conjunction with data processor 510,recordable data to be recorded to an electronic data storage. Recordingmodule 543 may generate, with data processor 510, a new data entryincluding recordable data for the electronic data storage. In someembodiments, recording module 543 may store, using data processor 510,the data entry in the electronic data storage in association withelectronic data storage account of a user to indicate that the userconducted the ownership transaction. In this case, recording module 543may determine, with data processor 510, the public address (e.g., hashedpublic key) associated with the user of user device 204 and record thedata entry in association with the public address.

Address database 550 may include any information related to addresses.Address database 550 may include a plurality of addresses. In addition,address database 550 may store a mapping between a plurality ofaddresses and a plurality of functions associated with electronic datastorage processing modules. The plurality of functions may be indicatedby a plurality of unique function identifiers (e.g., function names).

Recordable data format database 560 may include any information relatedto formatting of recordable data. Recordable data format database 560may include function identifiers associated with functions that enableconversion of recordable data with certain formats in association withinformation indicating details about the formats. Recordable data formatdatabase 560 may also store, in association with corresponding functionidentifiers, details about the formats of electronic data storage towhich the functions are meant to convert values from recordable data.Details about a format may include information indicating the order,lengths, as well as types of data fields.

Electronic data storage processing API 570 may comprise any informationrelated to conducting processing using electronic data storageprocessing modules. For example, electronic data storage processing API570 may include software, code, and data enabling server computer 500 toutilize electronic data storage processing modules to process recordabledata. In some embodiments, electronic data storage processing API 570may store information software, code, and data for implementing afunction in association with a function identifier corresponding to thefunction. In some cases, electronic data storage processing API 570 mayalso indicate a particular electronic data storage processing modulewith which a function indicated by its function identifier isassociated.

In some embodiments, the server computer may be a processor servercomputer. The processor server computer may include data processingsubsystems, networks, and operations. The processor server computer mayroute information between various computing devices. In some cases, theprocessor server computer may be utilized to support and deliverauthorization services, as well as clearing and settlement services. Insome embodiments, the processor server computer may be associated with apayment processing network (e.g., VisaNet® operated by Visa®), which mayinclude wired or wireless network, including the Internet.

FIG. 7 depicts a block diagram of an exemplary user device 602. FIG. 7shows a number of components, and user device 602 according toembodiments of the invention may comprise any suitable combination orsubset of such components.

User device 602 may include a processor 602D (e.g., a microprocessor)for processing functions of user device 602. One exemplary functionenabled by processor 602D includes processing functions of display 602Gto allow a user to see information (e.g., interfaces, contactinformation, messages, etc.). Processor 602D may include hardware withinuser device 602 that can carry out instructions embodied as code in acomputer-readable medium.

An exemplary processor may be a central processing unit (CPU). As usedherein, a processor can include a single-core processor, a plurality ofsingle-core processors, a multi-core processor, a plurality ofmulti-core processors, or any other suitable combination of hardwareconfigured to perform arithmetical, logical, and/or input/outputoperations of a computing device.

User device 602 may comprise a secure element 602A. Secure element 602Amay be a secure memory on user device 602 such that the data containedon secure element 602A cannot easily be hacked, cracked, or obtained byan unauthorized entity. Secure element 602A may be utilized by userdevice 602 to host and store data and applications that may require ahigh degree of security. Secure element 602A may be provided to userdevice 602 by a secure element issuer. Secure element 602A may be eitherembedded in the handset of user device 602 or in a subscriber identitymodule (SIM) card that may be removable from user device 602. Secureelement 602A can also be included in an add-on device such as amicro-Secure Digital (micro-SD) card or other portable storage device.

Secure element 602A may store any suitable sensitive information. Forexample, secure element 602A may store access data (e.g., accountinformation, token information, etc.) associated with a user. Otherinformation that may be stored in secure element 602A may include userinformation or user data (e.g., name, date of birth, contactinformation, etc.). In other embodiments, some, none, or all of theforegoing information may be stored in memory element 602C or may bestored at a remote server computer (e.g., in the cloud).

User device 602 may comprise a memory element 602C (e.g., computerreadable medium). Memory element 602C may be present within a body ofuser device 602 or may be detachable from the body of user device 602.The body of user device 602 may be in the form of a plastic substrate,housing, or other structure. Memory element 602C may store data (e.g.,applications, etc.) and may be in any suitable form (e.g., a magneticstripe, a memory chip, etc.).

Memory element 602C may comprise a mobile application 602B. Mobileapplication 602B may be computer code or data stored on a computerreadable medium (e.g. memory element 602C or secure element 602A) thatmay be executable by processor 602D to complete a task (e.g., provide aservice). Mobile application 602B may be an application that operates onuser device 602 and that may provide a user interface for userinteraction (e.g., to enter and view information).

In some embodiments, mobile application 602B may be a service providerapplication. Mobile application 602B may communicate with a serviceprovider computer to retrieve and return information during processingof any of a number of services offered to the user via user device 602(e.g., providing access to a resource).

User device 602 may further include a contactless element 602E, whichmay typically be implemented in the form of a semiconductor chip (orother electronic data storage element) with an associated wirelesstransfer (e.g., data transmission) element, such as an antenna 602F.Contactless element 602E may be associated with (e.g., embedded within)user device 602. Data or control instructions transmitted via a cellularnetwork may be applied to contactless element 602E by means of acontactless element interface (not shown). In some cases, thecontactless element interface may function to permit the exchange ofdata and/or control instructions between the user device circuitry (andhence the cellular network) and an optional contactless element 602E.

Contactless element 602E may be capable of transferring and receivingdata using a near-field communications (NFC) capability (or NFC medium)typically in accordance with a standardized protocol or data transfermechanism (e.g., ISO 14443/NFC). User device 602 may support contactlesstransactions using the EMV contactless communication protocol (EMV-CCP),which is based on ISO 14443, in order to interact with access devices(e.g., reader devices). This capability may typically be met byimplementing NFC. The NFC capability of user device 602 may be enabledby an embedded NFC chip or by the addition of an external memory card oraccessory that contains the NFC chip. NFC capability is a short-rangecommunications capability, such as RFID, Bluetooth®, infra-red, or otherdata transfer capability that can be used to exchange data between theuser device 602 and an interrogation device. Thus, user device 602 maybe capable of communicating and transferring data and/or controlinstructions via both cellular network and near-field communicationscapability.

User device 602 may further include an antenna 602F for wireless datatransfer (e.g., data transmission). Antenna 602F may be utilized by userdevice 602 to send and receive wireless communications. Antenna 602F mayassist in connectivity to the Internet or other communications networksand enable data transfer functions. Antenna 602F may enable SMS, USSD,as well as other types of cellular communications, such as voice calland data communications.

User device 602 may include a display 602G that may show information toa user. Display 602G may be any suitable screen that enables touchfunctionality. In some embodiments, display 602G of user device 602 maydisplay a user interface (e.g., of a mobile application or website) thatmay allow the user to select and interact with objects presented ondisplay 602G. The objects may include, but may not be limited to, menus,text fields, icons, and keys/inputs on a virtual keyboard.

User device 602 may include a speaker 602H, which may be any suitabledevice that can produce sound in response to an electrical audio signal.Speaker 602H may play recorded sounds, as well as prerecorded messagesto communicate with a user. In some cases, the user may be able toreceive instructions by voice communications played by speaker 602H towhich the user may respond (e.g., by returning voice command, activatinginput elements, etc.).

User device 602 may include a microphone 602I, which may be any suitabledevice that can convert sound to an electrical signal. Microphone 602Imay be utilized to capture one or more voice segments from a user. Forexample, microphone 602I may allow the user to transmit his or her voiceto user device 602. In some embodiments, the user may utilize voicecommands detected by microphone 602I to provide instructions to userdevice 602. In some cases, the user may provide voice commands detectedby microphone 602I to navigate through mobile application 602B.

User device 602 may further include input elements 602J to allow a userto input information into the device. Example input elements 602Jinclude hardware and software buttons, audio detection devices (e.g.,microphone), biometric readers, touch screens, and the like. A user mayactivate one or more of input elements 602J, which may pass userinformation to user device 602. In some cases, one or more of inputelements 602J may be utilized to navigate through various screens ofmobile application 602B.

In some embodiments, where user device 602 is a phone or other similarcomputing device, user device 602 may include a browser stored in thememory element 602C and may be configured to retrieve, present, and senddata across a communications network (e.g., the Internet). In suchembodiments, user device 602 may be configured to send data as part of atransaction. In some embodiments, user device 602 may provide the dataupon request from another entity (e.g., access device).

A computer system may be utilized to implement any of the entities orcomponents described above. Subsystems of the computer system may beinterconnected via a system bus. Additional subsystems may include aprinter, a keyboard, a fixed disk (or other memory comprising computerreadable media), a monitor, which is coupled to a display adapter, andothers. Peripherals and input/output (I/O) devices, which couple to anI/O controller (which can be a processor or other suitable controller),can be connected to the computer system by any number of means known inthe art, such as by a serial port. For example, the serial port orexternal interface can be used to connect the computer apparatus to awide area network such as the Internet, a mouse input device, or ascanner. The interconnection via system bus allows the central processorto communicate with each subsystem and to control the execution ofinstructions from system memory or the fixed disk, as well as theexchange of information between subsystems. The system memory and/or thefixed disk may embody a computer readable medium. In some embodiments,the monitor may be a touch sensitive display screen.

Specific details regarding some of the above-described aspects areprovided above. The specific details of the specific aspects may becombined in any suitable manner without departing from the spirit andscope of embodiments of the technology. For example, back endprocessing, data analysis, data collection, and other transactions mayall be combined in some embodiments of the technology. However, otherembodiments of the technology may be directed to specific embodimentsrelating to each individual aspect, or specific combinations of theseindividual aspects.

It should be understood that the present technology as described abovecan be implemented in the form of control logic using computer software(stored in a tangible physical medium) in a modular or integratedmanner. While the present invention has been described using aparticular combination of hardware and software in the form of controllogic and programming code and instructions, it should be recognizedthat other combinations of hardware and software are also within thescope of the present invention. Based on the disclosure and teachingsprovided herein, a person of ordinary skill in the art will know andappreciate other ways and/or methods to implement the present technologyusing hardware and a combination of hardware and software

Any of the software components or functions described in thisapplication, may be implemented as software code to be executed by aprocessor using any suitable computer language such as, for example,Java, C++ or Perl using, for example, conventional or object-orientedtechniques. The software code may be stored as a series of instructions,or commands on a computer readable medium, such as a random accessmemory (RAM), a read only memory (ROM), a magnetic medium such as ahard-drive or a floppy disk, or an optical medium such as a CD-ROM. Anysuch computer readable medium may reside on or within a singlecomputational apparatus, and may be present on or within differentcomputational apparatuses within a system or network.

The above description is illustrative and is not restrictive. Manyvariations of the technology will become apparent to those skilled inthe art upon review of the disclosure. The scope of the technologyshould, therefore, be determined not with reference to the abovedescription, but instead should be determined with reference to thepending claims along with their full scope or equivalents.

In some embodiments, any of the entities described herein may beembodied by a computer that performs any or all of the functions andsteps disclosed.

One or more features from any embodiment may be combined with one ormore features of any other embodiment without departing from the scopeof the technology.

A recitation of “a” “an” or “the” is intended to mean “one or more”unless specifically indicated to the contrary.

All patents, patent applications, publications, and descriptionsmentioned above are herein incorporated by reference in their entiretyfor all purposes. None is admitted to be prior art.

What is claimed:
 1. A method comprising: determining a data packetcomprising a) recordable data and b) address data for a plurality ofelectronic data storage processing modules run on one or more computers,the address data comprising a first address for a first electronic datastorage processing module and a second address for a second electronicdata storage processing module; sending, to a server computer, the datapacket with a request to record the recordable data to an electronicdata storage of a plurality of different electronic data storages; andreceiving a confirmation that the recordable data was recorded to theelectronic data storage.
 2. The method of claim 1, wherein therecordable data is routed to the first electronic data storageprocessing module using the first address and processed by the firstelectronic data storage processing module, and wherein the recordabledata is routed to the second electronic data storage processing moduleusing the second address and processed by the second electronic datastorage processing module.
 3. The method of claim 1, wherein the firstelectronic data storage processing module comprises an aggregator moduleand the second electronic data storage processing module comprises aformatter module.
 4. The method of claim 1, wherein at least some of theplurality of different electronic data storages are in different formatsand are used for recording different types of recordable data.
 5. Themethod of claim 1, wherein the plurality of different electronic datastorages are respectively adapted to record data for cryptocurrencytransactions, non-financial asset ownership transactions, and identityverification transactions.
 6. The method of claim 1, wherein the datapacket is a first data packet, the recordable data is first recordabledata, the electronic data storage is a first electronic data storage,the request is a first request, the confirmation is a firstconfirmation, and wherein the method further comprises: determining asecond data packet comprising a) second recordable data and b) addressdata for the plurality of electronic data storage processing modules runon the one or more computers, the address data comprising the firstaddress for the first electronic data storage processing module and athird address for the second electronic data storage processing module;sending, to a server computer, the second data packet with a secondrequest to record the recordable data to a second electronic datastorage of the plurality of different electronic data storages; andreceiving a second confirmation that the second recordable data wasrecorded to the second electronic data storage.
 7. The method of claim6, wherein the second recordable data is routed to the first electronicdata storage processing module using the first address and processed bythe first electronic data storage processing module, and wherein thesecond recordable data is routed to the second electronic data storageprocessing module using the third address and processed by the secondelectronic data storage processing module.
 8. A user device comprising:a processor; and a computer readable medium coupled to the processor,the computer readable medium comprising code, executable by theprocessor, to perform a method comprising: determining a data packetcomprising a) recordable data and b) address data for a plurality ofelectronic data storage processing modules run on one or more computers,the address data comprising a first address for a first electronic datastorage processing module and a second address for a second electronicdata storage processing module; sending, to a server computer, the datapacket with a request to record the recordable data to an electronicdata storage of a plurality of different electronic data storages; andreceiving a confirmation that the recordable data was recorded to theelectronic data storage.
 9. The user device of claim 8, wherein therecordable data is routed to the first electronic data storageprocessing module using the first address and processed by the firstelectronic data storage processing module, and wherein the recordabledata is routed to the second electronic data storage processing moduleusing the second address and processed by the second electronic datastorage processing module.
 10. The user device of claim 8, wherein thefirst electronic data storage processing module comprises an aggregatormodule and the second electronic data storage processing modulecomprises a formatter module.
 11. The user device of claim 8, wherein atleast some of the plurality of different electronic data storages are indifferent formats and are used for recording different types ofrecordable data.
 12. The user device of claim 8, wherein the pluralityof different electronic data storages are respectively adapted to recorddata for cryptocurrency transactions, non-financial asset ownershiptransactions, and identity verification transactions.
 13. The userdevice of claim 8, wherein the data packet is a first data packet, therecordable data is first recordable data, the electronic data storage isa first electronic data storage, the request is a first request, theconfirmation is a first confirmation, and wherein the method furthercomprises: determining a second data packet comprising a) secondrecordable data and b) address data for the plurality of electronic datastorage processing modules run on the one or more computers, the addressdata comprising the first address for the first electronic data storageprocessing module and a third address for the second electronic datastorage processing module; sending, to the server computer, the seconddata packet with a second request to record the recordable data to asecond electronic data storage of the plurality of different electronicdata storages; and receiving a second confirmation that the secondrecordable data was recorded to the second electronic data storage. 14.The user device of claim 13, wherein the second recordable data isrouted to the first electronic data storage processing module using thefirst address and processed by the first electronic data storageprocessing module, and wherein the second recordable data is routed tothe second electronic data storage processing module using the thirdaddress and processed by the second electronic data storage processingmodule.
 15. The user device of claim 8, wherein the user device is amobile phone.
 16. The user device of claim 8, wherein the user device isa motor vehicle or a wearable device.
 17. A system comprising: a userdevice comprising a processor, and a computer readable medium coupled tothe processor, the computer readable medium comprising code, executableby the processor, to perform a method comprising determining a datapacket comprising a) recordable data and b) address data for a pluralityof electronic data storage processing modules run on one or morecomputers, the address data comprising a first address for a firstelectronic data storage processing module and a second address for asecond electronic data storage processing module, sending, to a servercomputer, the data packet with a request to record the recordable datato an electronic data storage of a plurality of different electronicdata storages, and receiving a confirmation that the recordable data wasrecorded to the electronic data storage; and the server computer. 18.The system of claim 17, wherein the recordable data is routed to thefirst electronic data storage processing module using the first addressand processed by the first electronic data storage processing module,and wherein the recordable data is routed to the second electronic datastorage processing module using the second address and processed by thesecond electronic data storage processing module.
 19. The system ofclaim 17, wherein the user device is a mobile phone, a wearable device,or a motor vehicle.
 20. The system of claim 17, wherein the firstelectronic data storage processing module comprises an aggregator moduleand the second electronic data storage processing module comprises aformatter module.